Garbage Collection in an Uncooperative Environment

Accurate Garbage Collection in Uncooperative Environments with Lazy Pointer Stacks

Implementing a new programming language by the means of a translator to an existing language is attractive as it provides portability over all platforms supported by the host language and reduces the development time as many low-level tasks can be delegated to the host compiler. The C and C++ programming languages are popular choices for many language implementations due to the availability of ...

Accurate garbage collection in uncooperative environments revisited

Implementing a concurrent programming language such as Java by the means of a translator to an existing language is attractive as it provides portability over all platforms supported by the host language and reduces development time – as many low-level tasks can be delegated to the host compiler. The C and C++ programming languages are popular choices for many language implementations due to th...

Experience with Garbage Collection for Modula-2+ in the Topaz Environment

Topaz is an experimental distributed computing environment programmed in Modula-2+, which supports garbage collection. Topaz has been in daily use by about 50 researchers at SRC since 1986. The Modula-2+ garbage collector is concurrent; it combines reference-counting and mark-and-sweep collection. The principal challenges are to reduce the costs of the language primitives, and to reduce the tim...

Garbage Collection in an Object Oriented, Distributed, Persistent Environment

Garbage Collection: Automatic Memory Management in the Microsoft .NET Framework

Garbage collection in the Microsoft .NET common language runtime environment completely absolves the developer from tracking memory usage and knowing when to free memory. However, you’ll want to understand how it works. Part 1 of this two-part article on .NET garbage collection explains how resources are allocated and managed, then gives a detailed step-by-step description of how the garbage co...